Skip to content

Conversation

@gmethvin
Copy link
Member

For non-macOS platforms (Windows, Linux, etc.) storing in the keys.json file is preferable to storing in the individual MCP configuration files because:

  1. It can be updated or removed in one central location, rather than across several different client configuration files.
  2. We control the file so we can set restricted permissions.
  3. We can associate environment variables for PII, writes and sends with each key.

@gmethvin gmethvin force-pushed the store-keys-in-file branch 8 times, most recently from 25cb28f to 28bffe2 Compare November 18, 2025 21:35
@gmethvin gmethvin merged commit 49d50cf into main Nov 18, 2025
6 checks passed
[
"• API keys prompted interactively (never in shell history)",
"• macOS: Keys stored securely in Keychain",
"• Windows/Linux: Keys stored in ~/.iterable-mcp with file permissions",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

~/.iterable-mcp/keys.json

andymccutcheon pushed a commit to andymccutcheon/mcp-server that referenced this pull request Nov 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants